Just submitted this to Google accessibility support. What the actual hell is this timeline?
If you use TalkBack and navigate by exploring by touch rather than swiping, when you drag your finger over the player controls while a video is playing in the YouTube Android app, within seconds the entire app dies with a `StackOverflowError`. Over 4,500 frames of pure recursion before the 8 MB stack runs out.
Naturally, the app restarts, immediately reloads the exact same video and player state, and the second you touch the screen again to find the pause or seek controls, it blows up again.
I pulled `adb logcat -b crash` and it's a ridiculous infinite loop between Android's framework and Litho:
`View.dispatchTouchExplorationHoverEvent`.
-> `TouchDelegate.onTouchExplorationHoverEvent` (framework forwards hover event to delegate).
-> `ComponentHost.dispatchHoverEvent` (Litho forwards back to host).
-> `hdu.onTouchExplorationHoverEvent` (obfuscated TouchDelegate subclass.)
-> and back around forever.
From the looks of it, a `TouchDelegate`, presumably meant to enlarge the tap target for one of the smaller player controls, was given a delegate view that points right back to the `ComponentHost` that owns the delegate in the first place.
The best part? Normal touches don't hit `dispatchTouchExplorationHoverEvent`. Sighted users will never encounter this, and even blind users swiping through elements one at a time won't trigger it because linear navigation doesn't emit hover events. It strictly breaks explore by touch. Conveniently, the exact interaction model a huge chunk of us rely on to quickly locate controls.
I handed them the exact cycle, device specs, and the obfuscated frame name for build 21.34.243. Now taking bets on whether an engineer actually sees and fixes the root cause or if support tells me to reinstall the app and clear my cache.
